Hello,
In our project we decided to divide requirement module into other modules to decrease number of people working in the same module. Right now 20 people are writing and reviewing requirements. What I am trying to do is to modify the "Object Number" attribute of the requirements so the module shall start from 3.2.2 or 3.2.3 etc.. instead of 1.
Right now i am adding Empty headings to the beginning of modules and hide them using filters. But it is an awkward solution.
I searched the forum and understand that "Object Number" is not an attribute of object but related with the position of objects in module, therefore i was wondering if there is a way to change properties of module so module would start from 3.2.2 instead of 1.
Thank You.
Haeras - Wed Aug 25 04:41:30 EDT 2010 |
|
Re: Modify Object Number..
doors36677 - Wed Aug 25 10:55:18 EDT 2010
This can't be done by the user.
|
|
Re: Modify Object Number..
SystemAdmin - Wed Aug 25 22:50:11 EDT 2010
Haeras wrote: "....divide requirement module into other modules to decrease number of people working in the same module...."
Before embarking on breaking the module up into many modules, did you try using the DOORS "Shared Edit" feature which allow multiple authors to edit the same module at the same time? If yes, what aspect of the "Shared Edit" feature didn't work for you?
Paul Miller
|
|
Re: Modify Object Number..
Haeras - Thu Aug 26 02:57:33 EDT 2010 SystemAdmin - Wed Aug 25 22:50:11 EDT 2010
Haeras wrote: "....divide requirement module into other modules to decrease number of people working in the same module...."
Before embarking on breaking the module up into many modules, did you try using the DOORS "Shared Edit" feature which allow multiple authors to edit the same module at the same time? If yes, what aspect of the "Shared Edit" feature didn't work for you?
Paul Miller
|
|
Re: Modify Object Number..
kbmurphy - Thu Aug 26 10:09:49 EDT 2010 Haeras - Thu Aug 26 02:57:33 EDT 2010
Well actually number of developers going to work on modules is nearly twenty and probably number of sections would be more than fifty, without trying we come to conclusion that "Shared Edit" will be slow and hard to work. Now decision is made and we progressed a lot with shared modules, we cannot go back to single module and shared edit.
> Well actually number of developers going to work on modules is nearly twenty and probably number of sections would be more than fifty, without trying we come to conclusion that "Shared Edit" will be slow and hard to work. Now decision is made and we progressed a lot with shared modules, we cannot go back to single module and shared edit.
There is so much wrong with this statement. Yet another example of someone needing a consultant or competent DOORS person with experience who has decided to cheap out and try to figure everything out themselves without even knowing the proper questions to ask before starting.
This will be the first of your problems, Haeras.
|
|